why is this necessary? can you explain a bit more the workflow?
since you have other PR I want to understand the need for this.

Thanks for the contribution again @krrrr38

@jamengual Yes. Based on the #2798 (comment), currently we can trigger commands by atlantis plan, run plan and @GithubUser plan.

When we run multiple servers for a single repository, these commands are handled in all servers. In this case, we can consider following workarounds to figure out which servers should run them.

• use different @GithubUser token by servers.
  • CONS: GithubApp doesn't support this feature.
    • GithubApp bot user cannot be completed like @GithubAppSlug on Github UI.
• use different repo_config_file and set different base branch
  • When we use feat: customize atlantis.yaml file name in server side config #2798, we can use different atlantis.yaml.
  • CONS: To process or not by each server, for example, we can change base branches. If we use multiple servers which want to use the same repository and same base branch, we cannot trigger them one by one.
• use custom workflow to check extra args with COMMENT_ARGS
  • For example, we can use atlantis plan -- -var 'DUMMY=run-on-server1' and parse it.
  • CONS: it's a dirty hack.
• use different execution name
  • To process or not on each server, we can use different execution name by this PR feature.

In my case, I will run multiple servers which use the same base branches (for dev1 env and dev2 env with main branch). At that time, when I run atlantis apply command in one environment, I need this feature. (Putting I should run one atlantis server aside...)

It's possible to solve my problem by adding@GithubAppSlug support, but I think this feature is the most easiest way to handle it.

Thanks @krrrr38 for the contribution!!!

Thank you @krrrr38 ! All your work is very much appreciated. You have high quality PRs!